Security-activated operational components

ABSTRACT

Various methods and systems include exemplary implementations for a security-activated operational component. Possible embodiments include but are not limited to obtaining access to an object data file configured to implement various functional operation regarding one or more objects; verifying validity of an authorization code associated with the object data file; and controlling operation of the operational component to enable or prevent its activation pursuant to the authorization code in accordance with one or more predetermined conditions.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)).

RELATED APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/005,162 entitled CONTROL TECHNIQUE FOR OBJECTPRODUCTION RIGHTS, naming Edward K. Y. Jung, Royce A. Levien, Robert W.Lord, Mark A. Malamud, John D. Rinaldo, Jr., Clarence T. Tegreene, andLowell L. Wood, Jr. as inventors, filed 22 Dec. 2007, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

The present application also constitutes a continuation-in-part of U.S.patent application Ser. No. 12/012,504 entitled MANUFACTURING CONTROLSYSTEM, naming Edward K. Y. Jung, Royce A. Levien, Robert W. Lord, MarkA. Malamud, John D. Rinaldo, Jr., Clarence T. Tegreene, and Lowell L.Wood, Jr. as inventors, filed 31 Jan. 2008, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

The present application also constitutes a continuation-in-part of U.S.patent application Ser. No. 12/079,921 entitled SECURITY-ACTIVATEDPRODUCTION DEVICE, naming Edward K. Y. Jung, Royce A. Levien, Robert W.Lord, Mark A. Malamud, John D. Rinaldo, Jr., Clarence T. Tegreene, andLowell L. Wood, Jr. as inventors, filed 27 Mar. 2008, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat ttp://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present Applicant Entity (hereinafter “Applicant”) has providedabove a specific reference to the application(s)from which priority isbeing claimed as recited by statute. Applicant understands that thestatute is unambiguous in its specific reference language and does notrequire either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant is designating the present applicationas a continuation-in-part of its parent applications as set forth above,but expressly points out that such designations are not to be construedin any way as any type of commentary and/or admission as to whether ornot the present application contains any new matter in addition to thematter of its parent application(s).

All subject matter of the Related Applications and of any and allparent, grandparent, great-grandparent, etc. applications of the RelatedApplications is incorporated herein by reference to the extent suchsubject matter is not inconsistent herewith.

BACKGROUND

The present application relates generally to a security-activatedsystems, devices and processes.

SUMMARY

Some embodiments provide a method for securely controlling an operationcomponent, including obtaining access to an object data file configuredto create or produce or duplicate or process or test one or moreobjects; verifying validity of an authorization code associated with theobject data file; and responsive to said verifying validity, controllingthe operational component by enabling or preventing its functionalactivation based on compliance with one or more predeterminedconditions. In addition to the foregoing, other method aspects aredescribed in the claims, drawings, and text forming a part of thepresent application.

Other embodiments may provide a computer program product including acomputer readable medium configured to perform one or more acts forsecurely controlling an operational component, wherein one or moreinstructions provide for obtaining access to an object data fileconfigured to create or produce or duplicate or process or test one ormore objects; verifying validity of an authorization code associatedwith the object data file; and responsive to said verifying validity,controlling the operational component by enabling or preventing itsfunctional activation based on compliance with one or more predeterminedconditions. In addition to the foregoing, other computer program productaspects are described in the claims, drawings, and text forming a partof the present application.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for implementing theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

Further embodiments may provide a security system for one or moreoperational components, including an authorization code that requiresone or more pre-conditions to control an operational component that isconfigured to create or produce or duplicate or process or test anobject; a verification module capable of enabling or disabling theoperational component, the verification module operably coupled to theauthorization code and operably coupled to the operational component;and an object data file associated with the authorization code, whereinthe object data file is configured to activate the operational componentbased on confirmation from the verification module. In addition to theforegoing, other security-activated operational component aspects aredescribed in the claims, drawings, and text forming a part of thepresent application..

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of an exemplary computer architecture thatsupports the claimed subject matter of the present application.

FIG. 2 is a block diagram of an exemplary system that supports theclaimed subject matter of the present application.

FIGS. 3A, 3B, 3C, and 3D illustrate a flow diagram of an exemplarymethod in accordance with an embodiment of the subject matter of thepresent application.

FIG. 4 is a block diagram of an exemplary system that supports theclaimed subject matter of the present application.

FIGS. 5A, 5B and 5C illustrate a flow diagram of an exemplary method inaccordance with an embodiment of the subject matter of the presentapplication.

FIG. 6 is a block diagram of an exemplary system that supports theclaimed subject matter of the present application.

FIGS. 7A, 7B, 7C, and 7D illustrate a flow diagram of an exemplarymethod in accordance with an embodiment of the subject matter of thepresent application.

FIG. 8 illustrates a flow diagram of exemplary method features inaccordance with additional embodiments of the subject matter of thepresent application.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

In the description that follows, the subject matter of the applicationwill be described with reference to acts and symbolic representations ofoperations that are performed by one or more computers, unless indicatedotherwise. As such, it will be understood that such acts and operations,which are at times referred to as being computer-executed, include themanipulation by the processing unit of the computer of electricalsignals representing data in a structured form. This manipulationtransforms the data or maintains it at locations in the memory system ofthe computer which reconfigures or otherwise alters the operation of thecomputer in a manner well understood by those skilled in the art. Thedata structures where data is maintained are physical locations of thememory that have particular properties defined by the format of thedata. However, although the subject matter of the application is beingdescribed in the foregoing context, it is not meant to be limiting asthose of skill in the art will appreciate that some of the acts andoperations described hereinafter can also be implemented in hardware,software, and/or firmware and/or some combination thereof.

With reference to FIG. 1, depicted is an exemplary computing system forimplementing embodiments. FIG. 1 includes a computer 100, including aprocessor 110, memory 120 and one or more drives 130. The drives 130 andtheir associated computer storage media, provide storage of computerreadable instructions, data structures, program modules and other datafor the computer 100. Drives 130 can include an operating system 140,application programs 150, and program modules 160. Computer 100 furtherincludes user input devices 190 through which a user may enter commandsand data. Input devices can include an electronic digitizer, amicrophone, a keyboard and pointing device, commonly referred to as amouse, trackball or touch pad. Other input devices may include ajoystick, game pad, satellite dish, scanner, or the like.

These and other input devices can be connected to processor 110 througha user input interface that is coupled to a system bus, but may beconnected by other interface and bus structures, such as a parallelport, game port or a universal serial bus (USB). Computers such ascomputer 100 may also include other peripheral output devices such asspeakers, which may be connected through an output peripheral interface194 or the like.

Computer 100 may operate in a networked environment using logicalconnections to one or more computers, such as a remote computerconnected to network interface 196 The remote computer may be a personalcomputer, a server, a router, a network PC, a peer device or othercommon network node, and can include many or all of the elementsdescribed above relative to computer 100. Networking environments arecommonplace in offices, enterprise-wide area networks (WAN), local areanetworks (LAN), intranets and the Internet. For example, in the subjectmatter of the present application, computer 100 may comprise the sourcemachine from which data is being migrated, and the remote computer maycomprise the destination machine or vice versa. Note however, thatsource and destination machines need not be connected by a network 108or any other means, but instead, data may be migrated via any mediacapable of being written by the source platform and read by thedestination platform or platforms. When used in a LAN or WLAN networkingenvironment, computer 100 is connected to the LAN through a networkinterface 196 or an adapter. When used in a WAN networking environment,computer 100 typically includes a modem or other means for establishingcommunications over the WAN, such as the Internet or network 108. Itwill be appreciated that other means of establishing a communicationslink between the computers may be used.

According to one embodiment, computer 100 is connected in a networkingenvironment or a manufacturing machine either directly or via network108 such that processor 110 and/or program modules 160 can perform acontrol technique for object production rights system capable ofinstantiating a digital rights management module in accordance withembodiments herein.

Referring now to FIG. 2, illustrated is an exemplary block diagram foran embodiment of a duplication control system 200 for implementing acontrol technique for object production rights system. As shown,duplication control system 200 includes a processor 210, a memory 220,coupled to the processor 210. FIG. 2 also illustrates a transceiver 230which can be configured to send and receive one or more object datafiles or directly interact with a computing device 270 for receivingobject data files. FIG. 2 also illustrates digital rights managementmodule 240 accessible by processor 210 and by network 108 (see FIG. 1).FIG. 2 further illustrates a data store 250 coupled to processor 210.Digital rights management module 240 is configured to control digitalrights for object data files. In one embodiment, digital rightsmanagement module 240 is coupled to comparison module 260, which canalso be disposed within memory 220. In one embodiment, comparison module260 compares the digital rights management codes to a stored list ofdigital rights management codes to determine the authorization status asa function of the status of one or more previously compiled object datafiles. Comparison module 260 can further interact with object data filesresiding in memory 252, outside of memory 253, or in data store asobject data files 254. In one embodiment, object data files 252, 253and/or 254 include one or more computer-aided design (CAD) solid modelfiles configured to create three dimensional physical objects.

Data store 250 is configured to include authorization guideline data256. In one embodiment, the authorization guideline data can include onedigital certificates 2562, private/public key data 2564, one or moredigital rights management codes 2566 for manufacturing machines, and/ordigital rights management codes 2568. In one embodiment, authorizationguideline data includes list 2569 which can be a list of digital rightsmanagement codes, a list of object data files, or any list that couldbe, for example, associated with multiple manufacturing machines 290that require multiple authorization rights to be analyzed or the like.In one embodiment, list 2569 includes globally unique identifiers (GUID)that can function as digital rights management codes and providecryptographic control over the one or more object data files.

In the embodiment in which data store 250 includes object data files254, the object data files can be files that previously existed in datastore 250, or can be files that were previously received by theduplication control system 200 via transceiver 230, memory 220, network108.

In one embodiment, data store 250 stores digital rights management codesseparately from object data files, with the digital rights managementcodes decipherable with a public key, private key combination.

FIG. 2 further illustrates manufacturing machines 290(1-n) coupled tocontrol system 200. The multiple manufacturing machines 290(1-n) canallow manufacture of an object described by the one or more object datafiles according to permissions provided in the one or more digitalrights management codes.

In one embodiment, duplication control system 200 is coupled to each ofthe one or more manufacturing machines 290(1-n) to allow manufacture ofan object described by the one or more object data files according topermissions provided in the one or more digital rights management codes.

In one embodiment, manufacturing machines 290(1-n) are three-dimensionaladditive manufacturing machines configured for rapid prototyping,three-dimensional printing, two-dimensional printing, freeformfabrication, solid freeform fabrication, and stereolithography.

In another embodiment, manufacturing machines 290(1-n) can include asubtractive manufacturing machine, including machines adapted fordrilling, milling, turning, laser cutting, waterjet cutting, plasmacutting, wire electrical discharge cutting, cold, warm and hot forgingmetal fabrication, computer numerical controlled fabrication machine,and/or an additive manufacturing machine, and/or an injection moldingmachine.

In another embodiment, manufacturing machines 290(1-n) can include anextrusion manufacturing machine, a melting manufacturing machine, asolidification manufacturing machine, an ejection manufacturing machine,a die casting manufacturing machine, a stamping process machine.

In another embodiment, manufacturing machines 290(1-n) can include asubtractive manufacturing machine, including machines adapted fordrilling, milling, turning, laser cutting, waterjet cutting, plasmacutting, wire electrical discharge cutting, cold, warm and hot forgingmetal fabrication, computer numerical controlled fabrication machine,and/or an additive manufacturing machine, and/or an injection moldingmachine.

In another embodiment, manufacturing machines 290(1-n) can include amanufacturing machine configured to perform manufacturing using one ormore of metal, wood, ice, stone, glass, nuclear materials,pharmaceuticals, edible substances, sand, ceramic materials, aluminum,silicon, carbides, silicon nitrides, silicon carbides, metal/ceramiccombinations including aluminum/silicon nitride, aluminum/siliconcarbide, aluminum/zirconia and aluminum/aluminum nitride includingmaterials alterable by friction, heating and cooling.

It will be understood that the illustrated system embodiments of FIGS.1-2 are provide by way of example only, and are not intended to belimiting. Furthermore, it will be understood that the various processfeatures and system components disclosed herein may be incorporated indifferent embodiment combinations depending on the circumstances.

Referring now to FIGS. 3A, 3B, 3C and 3D an exemplary flow diagramillustrates the operation of a control technique for object productionrights system according to one or more embodiments.

As illustrated in FIG. 3A, block 310 provides for receiving at theduplication control system a digital rights management code, the digitalrights management code associated with one or more object data files(e.g., duplication control system 200 receiving digital rightsmanagement code associated with one or more object data file viacomputing deice 270, network 108, and/or manufacturing machine(s)290(1-n)). Depicted within block 310 is optional block 3102, whichprovides for receiving the digital rights management code as digitalrights management code decipherable with a public key, private keycombination (e.g., a duplication control system 200 receiving one ormore digital rights management code as cryptographically sealed coderequiring a public key, private key pair).

Depicted within block 310 is optional block 3104, which provides forreceiving the digital rights management code as a globally uniqueidentifier (GUID) predetermined for an owner of the one or more objectdata files, the GUID providing cryptographic control over the one ormore object data files (e.g., a duplication control system 200 receivingdigital rights management code as a globally unique identifier (GUID)predetermined for an owner of the one or more object data files, theGUID providing cryptographic control from a manufacturing machine 290,and/or computer 100).

Depicted within block 3104 is optional block 31041 which provides forreceiving the digital rights management code coupled to the one or moreobject data files (e.g., duplication control system 200 receivingdigital rights management code coupled to one or more object datafiles).

Depicted within block 3104 is optional block 31042 which provides forreceiving the digital rights management code separately from the one ormore object data files (e.g., duplication control system 200 receivingdigital rights management code in a separate transaction overtransceiver 230).

Depicted within block 30142 is optional block 310422 which provides forreceiving the digital rights management code coupled to the one or moreobject data files, the digital rights management code decipherable witha public key, private key combination (e.g., duplication control system200 receiving digital rights management code over network 108, fromcomputing device 270 and/or from manufacturing machine 290(1-n) whereinthe digital rights management code is protected by a public key, privatekey pair). In one embodiment the digital rights management codes can beglobally unique identifier (GUID) predetermined for an owner of the oneor more object data files, the GUID providing cryptographic control overthe one or more object data files. In other embodiments, the GUID can beassociated with a public/private key pair.

Also depicted within block 3104 is optional block 31044, which providesfor comparing the digital rights management code to a stored list of oneor more digital rights management codes to determine if any of the oneor more object data files are related to one or more previously compiledobject data files (e.g., comparison module 260 performing comparisons ofthe digital management code with a stored list in data store 250 ofdigital rights management codes to determine if the object data filesare related to one more previously compiled object data files, theobject data files can be received via manufacturing machine 290(1-n),computing device 270 and/or computing device 280 over network 109).Optional block 31044 is coupled to optional block 31046 which providesfor determining a status of the one or more previously compiled objectdata files (e.g., digital rights management module 240 determining astatus of the previously compiled object data files).

Optional block 31046 is further coupled to optional block 31048 whichprovides for determining the authorization status as a function of ausage status of the one or more previously compiled object data files(e.g., digital rights management module 240 determining a status as afunction of a usage status of the previously compiled object datafiles).

Optional block 31048 includes optional block 310482 which provides fordetermining a usage status according to a compiling history of theobject data files, the compiling history providing data related to aprior manufacturing history including one or more of a materials needshistory, a manufacturing result history, and a manufacturing time (e.g.,digital rights management module 240 determining a status of thepreviously compiled object data files received via network 108,computing device 270, manufacturing machines 290(1-n) and/or data store250).

Block 31048 further depicts optional block 310484, which provides fordetermining a usage status according to a compiling history of theobject data files, the compiling history providing data related to aprior manufacturing history including a trouble history affecting theauthorization status (e.g., digital rights management module 240determining a status of the previously compiled object data filescompiling history and trouble history affecting an authorization statusreceived via network 108, computing device 270, manufacturing machines290(1-n) and/or data store 250).

Further depicted within block 31048 is optional block 310486 whichprovides for determining a usage status according to a compiling historyof the object data files, the compiling history providing data relatedto a prior manufacturing history including a location of manufacturinghistory indicative of one or more of a number of locations ofcompilation and/or a number of compilations at a manufacturing location(e.g., digital rights management module 240 determining a number oflocations of compilation and/or number of compilations of the previouslycompiled object data files received via network 108, computing device270, manufacturing machines 290(1-n) and/or data store 250).

Optional block 31048 further depicts optional blocks 310488 and 310489.Optional block 310488 provides for determining a usage status accordingto a number of times the one or more object data files had been compiled(e.g., digital rights management module 240 determining a status of thepreviously compiled object data files received via network 108,computing device 270, manufacturing machines 290(1-n) and/or data store250). Optional block 31049 provides for comparing the usage status witha permission associated with the digital rights management code (e.g.,digital rights management module 240 determining a status of thepreviously compiled object data files received via network 108,computing device 270, manufacturing machines 290(1-n) and/or data store250 and comparing via comparison module 260 a usage status with apermission associated with the digital rights management code).

Referring now to FIG. 3B, the flow diagram depicting a method accordingto an embodiment continues. Specifically, block 310 further depictsoptional block 3105, which provides for receiving at the duplicationcontrol system the digital rights management code, the duplicationcontrol system integrated with one or more three-dimensionalmanufacturing machines to perform additive manufacturing using one ormore of ABS (Acrylonitrile/butadiene/styrene), ABSi (ABS with highimpact strength), ABS M-30 (Acrylonitrile/butadiene/styrene), PC(Polycarbonate), PC-ISO (Polycarbonate-ISO), PC/ABS (Polycarbonate/ABSBlend), PPSF (Polyphenylsulfone), clear and/or colored resin (e.g.,duplication control system 200 receiving digital rights management code,wherein duplication control system 200 is integrated with one or more ofmanufacturing machines 290(1-n) that perform three-dimensionalmanufacturing to perform additive manufacturing).

Block 310 further depicts optional block 3106, which provides forreceiving at the duplication control system the digital rightsmanagement code, the duplication control system integrated with one ormore three-dimensional manufacturing machines to perform manufacturingusing one or more of metal, wood, ice, stone, glass, nuclear materials,pharmaceuticals, edible substances, sand, ceramic materials, aluminum,silicon, carbides, silicon nitrides, silicon carbides, metal/ceramiccombinations including aluminum/silicon nitride, aluminum/siliconcarbide, aluminum/zirconia and aluminum/aluminum nitride includingmaterials alterable by friction, heating and cooling (e.g., duplicationcontrol system 200 receiving digital rights management code, whereinduplication control system 200 is integrated with one or more ofmanufacturing machines 290(1-n) that perform three-dimensionalmanufacturing to perform manufacturing of metal, wood, ice, stone,glass, nuclear materials, pharmaceuticals, edible substances, sand,ceramic materials, aluminum, silicon, carbides, silicon nitrides,silicon carbides, and/or metal/ceramic combinations).

Block 310 further depicts optional block 3107, which provides forreceiving at the duplication control system the digital rightsmanagement code, the duplication control system integrated with one ormore two-dimensional manufacturing machines to perform manufacturingusing one or more of skin, textiles, edible substances, paper, siliconprinting (e.g., duplication control system 200 receiving digital rightsmanagement code, wherein duplication control system 200 is integratedwith one or more of manufacturing machines 290(1-n) to performtwo-dimensional manufacturing).

Block 310 further depicts optional block 3108, which provides forreceiving at the duplication control system the one or more object datafiles wherein the one or more object data files are three-dimensionalobject data files including at least one or more computer-aided design(CAD) solid model files configured to create one or more threedimensional physical objects (e.g., duplication control system 200receiving digital rights management code, wherein duplication controlsystem 200 is integrated with one or more of manufacturing machines290(1-n) to perform three-dimensional manufacturing of CAD files.

Referring now to FIG. 3C, the flow diagram depicting a method inaccordance with an embodiment continues. Block 320 illustrates an aspectfor generating an authorization status based on the digital rightsmanagement code (e.g., digital rights management module 240 generatingthe authorization status based on received or stored digital rightsmanagement code). Depicted within block 320 is optional block 3202 whichprovides for comparing the digital rights management code to a machineidentifier associated with the one or more manufacturing machines todetermine whether any of the one or more manufacturing machines isauthorized to produce an object described in the object data files (e.g.comparison module 260 comparing the digital rights management code to amachine identifier supplied by one or more of manufacturing machines290(1-n)).

Block 320 further depicts optional block 3204 which provides forcomparing the digital rights management code to a database of digitalrights management codes, the database providing the authorization statusassociated with the digital rights management code (e.g., comparisonmodule 260 comparing the digital rights management code to a database indata store 250 storing digital rights management codes, includingauthorization status).

Depicted within optional block 3204 is optional block 32042 whichprovides for comparing the digital rights management code to thedatabase of digital rights management codes to determine one or more ofa licensing status, a royalty status, an expiration date pertaining to alicense, and a number of manufacturing runs permitted according to alicense (e.g., comparison module 260 comparing the digital rightsmanagement code to determine a licensing status, royalty status,expiration date, number of times a license permits a manufacturing runand the like).

Referring now to FIG. 3D, the flow diagram continues illustrating themethod in accordance with an embodiment with block 330. Specifically,block 330 illustrates an aspect for configuring one or moremanufacturing machines to operate as a function of the authorizationstatus (e.g., processor 210 and digital rights management moduleconfiguring one or more manufacturing machines 290(1-n) to operate inaccordance with the authorization status determined by comparison module260).

Depicted within block 330 is optional block 3302 which provides forenabling the one or more manufacturing machines to operate if theauthorization status provides permission for operation wherein the oneor more manufacturing machines perform one or more of rapid prototyping,three-dimensional printing, two-dimensional printing, freeformfabrication, solid freeform fabrication, and stereolithography (e.g.,digital rights management module 240 interacting with one or more ofmanufacturing machines 290(1-n) to operate according the authorizationstatus).

Also depicted within block 330 is optional block 3304 which provides forenabling the one or more manufacturing machines to operate if theauthorization status provides permission for operation wherein the oneor more manufacturing machines include a subtractive manufacturingmachine, including machines adapted for drilling, milling, turning,laser cutting, waterjet cutting, plasma cutting, wire electricaldischarge cutting, cold, warm and hot forging metal fabrication,computer numerical controlled fabrication machine, and/or an additivemanufacturing machine, and/or an injection molding machine (e.g.,digital rights management module 240 interacting with the one or moremanufacturing machines 290(1-n) to operate if the authorization statusprovides permission for operation, the one or more manufacturingmachines 290(1-n) including subtractive manufacturing machines).

Further depicted within block 330 is optional block 3306 which providesfor enabling the one or more manufacturing machines to operate if theauthorization status provides permission for operation wherein the oneor more manufacturing machines include one or more of an extrusionmanufacturing machine, a melting manufacturing machine, a solidificationmanufacturing machine, an ejection manufacturing machine, a die castingmanufacturing machine, a stamping process machine (e.g., digital rightsmanagement module 240 interacting with the one or more manufacturingmachines 290(1-n) to operate if the authorization status providespermission for operation, the one or more manufacturing machines290(1-n) can include an extrusion manufacturing machine, a meltingmanufacturing machine, a solidification manufacturing machine, anejection manufacturing machine, a die casting manufacturing machine, astamping process machine or the like).

Referring now to the schematic depiction of FIG. 4, illustrated is anexemplary block diagram for an embodiment of a manufacturing controlsystem 400 for controlling digital production rights for producing aphysical object. As shown, manufacturing control system 400 includes amemory 420 coupled to the processor 410. Manufacturing control system400 further includes transceiver 430 that is shown to be coupled throughoptional controller 470 to processor 410. FIG. 4 also illustratestransceiver 430 which can be configured to send and receive one or moreobject data files or directly interact with a computing device 482 forreceiving object data files. FIG. 4 also illustrates digital rightsconfirmation module 440 accessible by processor 410 and by network 108(see FIG. 1). FIG. 4 further illustrates a data store 450 and anauthorization module 455 coupled to processor 410.

Digital rights confirmation module 440 is configured to control digitalrights for object data files 452, 453 and/or 454. Authorization module455 is configured for enabling a manufacturing machine (e.g.,manufacturing machines 497, 498) to interface with an object data fileonly if an authorization code 458 meets one or more predeterminedconditions. In one embodiment, digital rights confirmation module 440 iscoupled to authorization module 455 and to comparison module 460, whichcan also be disposed within memory 420. In one embodiment, comparisonmodule 460 compares one or more authorization codes to a stored list ofdigital rights management codes to determine the authorization status asa function of the status of one or more previously compiled object datafiles. Comparison module 460 can further interact with object data files452, object data files 453, or object data files 454. In one embodiment,object data files 452, 453 and/or 454 include one or more computer-aideddesign (CAD) solid model files configured to create three dimensionalphysical objects. In other embodiments the object data files areconfigured to create two-dimensional objects, renderings, prototypes andthe like. Data store 450 is configured to include authorizationguideline data 456 such as authorization code(s) 458 or other digitalrights authorization data. In the embodiment in which data store 450includes object data files 454, the object data files can be files thatpreviously existed in data store 450, or can be files that werepreviously received by the manufacturing control system 400 viatransceiver 430, memory 420, network 108.

FIG. 4 further illustrates manufacturing machines coupled to controlsystem 400. Specifically, manufacturing control system 400 isillustrated coupled to subtraction machine 491, stamping machine 492,extrusion machine 493, melting machine 494, die-casting machine 495,solidifying machine 496, and generic manufacturing machine 497.Manufacturing control system 400 is further coupled to manufacturingmachine 498 via network 108 and computing device 480. In one embodiment,subtraction machine 491 can be configured with a controller 472 and bealternatively coupled to manufacturing control system via network 108 ordirectly. Subtraction machine 491 illustrates an exemplary manufacturingmachine with a controller 472 to control digital production rightsdirectly and/or over a network connection. Likewise, manufacturingmachine 498 could be coupled to a controller located in computing device480 or receive control directions from manufacturing control system 400.Each of manufacturing machines 491-498 can allow manufacture of anobject described by the one or more object data files as directed bymanufacturing control system 400 and controllers 470 and 472.

As shown, manufacturing machines 491-498 can be three-dimensionaladditive manufacturing machines configured for rapid prototyping,three-dimensional printing, two-dimensional printing, freeformfabrication, solid freeform fabrication, and stereolithography.

Manufacturing machines 491-498 include a subtractive manufacturingmachine 491, which can be adapted for drilling, milling, turning, lasercutting, waterjet cutting, plasma cutting, wire electrical dischargecutting, cold, warm and hot forging metal fabrication, computernumerical controlled fabrication machine, and/or an additivemanufacturing machine, and/or an injection molding machine.

Manufacturing machines 491-498 are shown including an extrusionmanufacturing machine 493, a melting manufacturing machine 494, asolidification manufacturing machine 496, a die casting manufacturingmachine 495, a stamping process machine 492, and a generic manufacturingmachine 497 which can be configured as an ejection manufacturingmachine.

In another embodiment, manufacturing machines 497 and/or 498 can beconfigured to perform manufacturing using one or more of metal, wood,ice, stone, glass, nuclear materials, pharmaceuticals, ediblesubstances, sand, ceramic materials, aluminum, silicon, carbides,silicon nitrides, silicon carbides, metal/ceramic combinations includingaluminum/silicon nitride, aluminum/silicon carbide, aluminum/zirconia,aluminum/aluminum nitride including materials alterable by friction,heating and cooling.

In another embodiment, manufacturing machines 497 and/or 498 can includea manufacturing machine configured as two-dimensional manufacturingmachines configured to perform manufacturing of one or more of skin,textiles, edible substances, paper and/or silicon printing.

Referring now to FIG. 5A, 5B and 5C, a flow diagram illustrates a methodin accordance with an embodiment. Block 510 provides for identifying atleast one object data file configured to produce an object by amanufacturing machine (e.g., controller 470 and/or 472 identifyingobject data files 452, 453, 454 to produce an object by manufacturingmachines 497, 498, and/or subtraction machine 491, stamping machine 492,extrusion machine 493, melting machine 494, die-casting machine 495and/or solidifying machine 496). Disposed within block 510 is optionalblock 5102 which provides for receiving a file at a control systemcoupled to the manufacturing machine, the control system receiving thefile including the authorization code and the object data file as one ormore of a binary file and/or a stereolithography (STL) file and/or acomputer-aided design (CAD) solid model file and/or a self executingdata file and/or a basic machine tool instruction file (e.g.,transceiver 430 in control system 400 receiving object data files 452,453, 454). Further disposed in block 510 is optional block 5104 whichprovides for identifying the at least one object data file, wherein theobject data file is configured to produce the object via attaching,printing, painting, engraving and/or tattooing by the manufacturingmachine (e.g., transceiver 430 and control system 400 identifying objectdata files 452, 453, 454). Further disposed in block 510 is block 5105which provides for receiving the object data file as a computer-aideddesign (CAD) model file configured to create one or more physicalobjects, the object data file including the authorization codeconfigured as a checksum of the CAD model file (e.g., transceiver 430receiving object data files 452, 453, 454 including authorization codeconfigured as a checksum of a CAD model file).

Disposed within block 5105 is optional block 51052, which provides forenabling the manufacturing machine to interface with the object datafile when the one or more predetermined conditions are met, the one ormore predetermined conditions including a pass condition following alogical operation on the checksum (e.g., controller 470, controller 472and/or processor 410 enabling manufacturing machines 497, 498, and/orsubtraction machine 491, stamping machine 492, extrusion machine 493,melting machine 494, die-casting machine 495 and/or solidifying machine496 to interface with object data files 452, 453, and/or 454 whenpredetermined conditions are met, including a pass condition).

Further disposed in block 510 is optional block 5107 and optional block5108. Optional block 5107 provides for extracting the authorization codeas a checksum code (e.g., processor 410, controller 470 and/orcontroller 472 extracting authorization code from object data files 452,453 and/or 454). Optional block 5108 provides for comparing the checksumcode to a stored checksum code, the stored checksum code determined by agenerated machine identifier associated with the manufacturing machine(e.g. comparison module 460 comparing checksum code to checksum codestored in data store 450 and/or manufacturing machines 497, 498, and/orsubtraction machine 491, stamping machine 492, extrusion machine 493,melting machine 494, die-casting machine 495 and/or solidifying machine496).

Further disposed in block 510 is optional block 5109 which provides forenabling the manufacturing machine to perform if the authorization codemeets the one or more predetermined conditions, including performingadditive manufacturing using one or more of a metal, ABS(Acrylonitrile/butadiene/styrene), ABSi (ABS with high impact strength),ABS M-30 (Acrylonitrile/butadiene/styrene), PC (Polycarbonate), PC-ISO(Polycarbonate-ISO), PC/ABS (Polycarbonate/ABS Blend), PPSF(Polyphenylsulfone), clear and/or colored resin (e.g., controller 470,472 and/or control system 400 enabling manufacturing machines 497, 498,and/or subtraction machine 491, stamping machine 492, extrusion machine493, melting machine 494, die-casting machine 495 and/or solidifyingmachine 496 to perform if the authorization code meets the one or morepredetermined conditions).

Block 520 provides for confirming that an authorization code isassociated with the object data file, the authorization code configuredto be received by the manufacturing machine, the manufacturing machineadapted to receive the authorization code (e.g. controller 470 and/or472 and/or manufacturing control system 400 confirming that anauthorization code is associated with one or more of object data files452, 453, and/or 454 to be received by one or more of manufacturingmachines 491-498. Depicted within block 520 is optional block 5202 whichprovides for removing a header from a file, the header including theauthorization code, the file organized to include the header and theobject data file (e.g. processor 410 removing a header from one or moreof object data files 452, 453 and/or 454, the header including theauthorization code). Further depicted in block 520 is optional block5204 which provides for running an application to extract theauthorization code, the application configured to run a hash algorithm,the application determining whether the one or more predeterminedconditions are met (e.g., processor 410 running an application (e.g.,application 679) or an application stored in memory 420 to extract anauthorization code from one or more of object data files 452, 453,and/or 454).

Block 530 provides for enabling the manufacturing machine to interfacewith the object data file only if the authorization code meets one ormore predetermined conditions (e.g., controller 470, 472 and/or controlsystem 400 enabling manufacturing machines 497, 498, and/or subtractionmachine 491, stamping machine 492, extrusion machine 493, meltingmachine 494, die-casting machine 495 and/or solidifying machine 496 tointerface with object data files 452, 453, and/or 454 only if theauthorization code meets one or more predetermined conditions). Depictedwithin block 530 is optional block 5302 which provides for enabling aphysical component of the manufacturing machine to function if theauthorization code meets the one or more predetermined conditions (e.g.,controller 470, 472 and/or control system 400 enabling physicalcomponent within or attached to manufacturing machines 497, 498, and/orsubtraction machine 491, stamping machine 492, extrusion machine 493,melting machine 494, die-casting machine 495 and/or solidifying machine496 to function if the authorization code meets predeterminedconditions). Also depicted within block 530 is optional block 5304,which provides for enabling a read function of the manufacturing machineif the authorization code meets a checksum requirement prior to openingthe object data file (e.g., controller 470, 472 and/or control system400 enabling a read function of manufacturing machines 497, 498, and/orsubtraction machine 491, stamping machine 492, extrusion machine 493,melting machine 494, die-casting machine 495 and/or solidifying machine496 if the authorization code meets a checksum requirement). Furtherdepicted within block 530 is optional block 5306 which provides forenabling a physical component of the manufacturing machine to functionif the authorization code matches one or more codes in an accessiblelist of codes coupled to the manufacturing machine (e.g., controller470, 472 and/or control system 400 enabling a physical component ofmanufacturing machines 497, 498, and/or subtraction machine 491,stamping machine 492, extrusion machine 493, melting machine 494,die-casting machine 495 and/or solidifying machine 496 if theauthorization code matches an accessible list of codes). Furtherdepicted within block 530 is optional 5308 which provides for enablingthe object data file to become readable by the manufacturing machine ifthe authorization code matches a machine identifier associated with themanufacturing machine (e.g., controller 470, 472 and/or control system400 enabling one or more of object data files 452, 453, and/or 454 tobecome readable by one or more of manufacturing machines 497, 498,and/or subtraction machine 491, stamping machine 492, extrusion machine493, melting machine 494, die-casting machine 495 and/or solidifyingmachine 496 if the authorization code matches a machine identifierassociated with the one or more manufacturing machines 491-498).

Block 540 provides for enabling the manufacturing machine to perform oneor more of stereolithography (SLA), selective laser sintering (SLS),computer numerical control (CNC), and fused deposition modeling (FDM) ifthe authorization code meets the one or more predetermined conditions(e.g., controller 470, 472 and/or control system 400 enabling one ormore of manufacturing machines 497, 498, and/or subtraction machine 491,stamping machine 492, extrusion machine 493, melting machine 494,die-casting machine 495 and/or solidifying machine 496 to perform one ormore of stereolithography (SLA), selective laser sintering (SLS),computer numerical control (CNC), and fused deposition modeling (FDM) ifthe authorization code meets the one or more predetermined conditions).

Block 550 provides for enabling the manufacturing machine to perform ifthe authorization code meets the one or more predetermined conditions,including performing additive manufacturing using one or more of ABS(Acrylonitrile/butadiene/styrene), ABSi (ABS with high impact strength),ABS M-30 (Acrylonitrile/butadiene/styrene), PC (Polycarbonate), PC-ISO(Polycarbonate-ISO), PC/ABS (Polycarbonate/ABS Blend), PPSF(Polyphenylsulfone), clear and/or colored resin (e.g., controller 470,472 and/or control system 400 enabling one or more of manufacturingmachines 497, 498, and/or subtraction machine 491, stamping machine 492,extrusion machine 493, melting machine 494, die-casting machine 495and/or solidifying machine 496 to perform if the authorization codemeets the one or more predetermined conditions).

Block 560 provides for enabling the manufacturing machine to perform ifthe authorization code meets the one or more predetermined conditions,including performing three-dimensional manufacturing using one or moreof metal, wood, ice, stone, glass, nuclear materials, pharmaceuticals,edible substances, sand, ceramic materials, aluminum, silicon, carbides,silicon nitrides, silicon carbides, metal/ceramic combinations includingaluminum/silicon nitride, aluminum/silicon carbide, aluminum/zirconiaand aluminum/aluminum nitride including materials alterable by friction,heating and cooling (e.g., controller 470, 472 and/or control system 400enabling one or more of manufacturing machines 497, 498, and/orsubtraction machine 491, stamping machine 492, extrusion machine 493,melting machine 494, die-casting machine 495 and/or solidifying machine496 to perform if the authorization code meets the one or morepredetermined conditions).

Block 570 provides for enabling the manufacturing machine to perform ifthe authorization code meets the one or more predetermined conditions,including manufacturing using one or more of skin, textiles, ediblesubstances, paper, and silicon printing (e.g. controller 470, 472 and/orcontrol system 400 enabling one or more of manufacturing machines 497,498, and/or subtraction machine 491, stamping machine 492, extrusionmachine 493, melting machine 494, die-casting machine 495 and/orsolidifying machine 496 to perform if the authorization code meets theone or more predetermined conditions).

Referring now to FIG. 6, an exemplary embodiment of a security controlsystem 600 is illustrated. More particularly, FIG. 6 illustrates asecurity control system 600 including one or more operational components610; authorization code(s) 620 that requires one or more pre-conditionsfor controlling operation of an operational component 610, andverification module 630 capable of enabling or disabling an operationalcomponent 610. Verification module 630 is shown operably coupled toauthorization code(s) 620, which can be stored locally as well asreceived via buffer 660 and/or transceiver 670. The buffer 660 shown indashed lines is coupled to the verification module 630 and totransceiver 670. It will be understood that the buffer 660 can beconfigured to send an acknowledgement that the object data file wasreceived by the security control system 600. In one embodiment,transceiver 670 can be configured to operate as a buffer. In otherembodiments, transceiver 670 can function only as a transmitting devicecoupled to a separate buffer 660 as will be appreciated by one of skillin the art. In either case, according to an embodiment, buffer 660 ortransceiver 670 configured as a buffer can be adapted for processingobject data file(s) 640 to verify a request to implement (e.g.,instantiate) the object data file 640 received from input module 680.

Verification module 630 can include authorization codes 620 as a datastore of authorization code(s) 620 within verification module 630 or asseparately received authorization codes via input module 680. In someinstances an input module 680 may be incorporated as part of thesecurity control system 600. In one embodiment, inputs 676 and 678received from an external control system 675 can be associated with anoperational component for creating, producing, duplicating, processing,or testing an object in accordance with a security technique disclosedherein. For example, input 676 and/or input 678 could be adapted toenable creating, producing, duplicating, processing, and/or testing inaccordance with authorization code(s) 620. As one of skilled in the artwith the benefit of the present application will appreciate, input 676could be configured to serve as an internal source of object data,applications (e.g., see 679) and the like.

Security control system 600 also includes object data file(s) 640,associated with authorization code(s) 620. Object data file(s) 640 areconfigured to enable an operational component 610 to initiate or preventan operational function regarding an operational output (see outputobjects 650, output data 652, output result 654) based on confirmationor preventive indications from verification module 630 and/orauthorization code(s) 620 in accordance with a predetermined condition.Object data file(s) 640 can be configured as operational instructions,production model files, computer-aided manufacturing (CAM) files, and/orcomputer-aided design (CAD) solid model files or the like.

In one embodiment, security control system 600 includes buffer 660 thatis adapted to receive the authorization code(s) 620 and notifyverification module 630 that an object data file(s) 640 is loaded inbuffer 660 and/or transceiver 670 configured to operate as a buffer.

In one embodiment, verification module 630 is configured to extractauthorization code(s) 620 from object data file(s) 640 so that theauthorization code(s) 620 can enable the security control system 600 toacknowledge the object data file as a valid file or invalid file.Alternatively or additionally, verification module 630 can be configuredto extract the authorization code(s) 620 which could include varioussecurity implementations such as, for example, a redundancy check, errorchecking algorithm, checksum, and/or cryptographic hash functioncode(s). In another embodiment, verification module 630 includes aparser 682 configured for removing a header from the object data file(s)640. In one embodiment, the header can include authorization code(s)620. Verification module 630 can also be configured to includetransceiver 670 to receive authorization code(s) 620 via input module680. In some instances, transceiver 670 can be coupled to both anexternal control system 675 and an operational component 610 to receivean enabling signal from the external control system 675 to enableimplementation of an operational output (see output objects 650, outputdata 652, output result 654).

In another embodiment, verification module 630 includes a comparator 683to compare authorization code(s) 620 to a stored list of authorizationcodes 625 accessible to an operational component 610 via verificationmodule 630 or by a stored list 625 within an operational component 610.The comparator 683 and/or another element outside verification module630 can be configured to generate an authorization code validation aswell as to receive an indication from external control system 675 viainput module 680 that authorization code(s) 620 are verified as valid.

In one embodiment, verification module 630 is configured for verifyingauthorization code(s) 620 that include data concerning copyrightprotection of the object data files) 640. For example, object datafile(s) 640 can include reproducible object files to enable anoperational component 610 to implement (e.g. reify) an operationaloutput (see 650, 652, 654). In another embodiment, verification module630 operates to verify authorization code(s) 620 wherein theauthorization code is associated with a pre-condition that may include alicensing status associated with the one or more objects and/or objectdata file.

The licensing status may ins some embodiments be indicative of one ormore of a royalty status, an expiration date pertaining to a license,and/or a number of manufacturing runs permitted according to thelicense, as well as other pertinent licensing requirements 672. In oneembodiment the license information including licensing requirements 672can be accessed locally by security control system 600, or in someinstances from an outside source via input module 680.

In another embodiment, verification module 630 is configured forverifying authorization code(s) 620 to determine a payment status and/oran authorization status under a permission agreement 674. The permissionagreement 674 can include an intellectual property licensing agreement,a private party ownership agreement, or any other agreement associatedwith creating, producing, duplicating, processing, or testing objects toimplement an exemplary functional operation involving one or more outputobjects 650, output data 652 and/or output result 654. In one embodimentthe permission agreement 674 that includes various predeterminedconditions can be accessed locally by security control system 600, or insome instances from an outside source via input module 680.

FIG. 6 further illustrates various embodiments of a security controlsystem 600 that can include one or more an operational components 610having security control features to enable or prevent various exemplaryfunctional operations that may include two-dimensional manufacturingtechniques, three-dimensional manufacturing techniques, additivemanufacturing units, and/or subtractive manufacturing using exemplaryindustrial or commercial production methods and/or operationalcomponents shown as production device 684, testing device 685, creativetool 686, duplication unit 687, packaging assembly 688, chemical process689, injection molding unit 690, subtraction machine 691, stampingmachine 692, extrusion machine 693, melting machine 694, die-castingmachine 695, solidifying machine 696, customized manufacturing machine697, rapid prototyping device 698, and robotic manufacturing line 699.

An operational component 610 can, in one embodiment, interact withverification module 630 to enable or prevent functioning of a physicalaspect of an operational component 610 (e.g., one or more of theillustrated operational components 684-699) if the authorization code(s)620 meet one or more predetermined conditions, such as a code thatcryptographically interacts with an operational component 610 to producea binary output to a switch or the like. In another embodiment,verification module 630 can prevent or enable a read function in one ormore of verification module 630 and/or an operational component 610 ifthe authorization code(s) 620 is accepted from external control system675 via input module 680 or is validated locally by verification module630.

In a further embodiment, verification module 630 is configured forenabling or disabling an operational component 610 dependent on one ormore predetermined conditions. Examples of such predetermined conditions(e.g., licensing restrictions 672, permission agreement 674) applicableto one or more of the operational components 610 may include but are notlimited to one or more of the following: benchmark comparison, temporalmilestone, time period restriction, production quantity limitation,production machine qualification, operator qualification, eventoccurrence, and quality certification.

In another embodiment, verification module 630 enables (or in someinstances prevents) object data file(s) 640 to become readable by anoperational component 610 if the authorization code(s) 620 passes acompare function performed by comparator 683 associated with a machineidentifier passed to comparator 683 from an operational component 610.

Referring now to FIGS. 7A, 7B, 7C, and 7D, a flow diagram illustrates amethod in accordance with various embodiments for a security-activatedoperational component. FIG. 7A illustrates block 710, which provides forobtaining access to an object data file configured to produce one ormore objects by an operational component (e.g., an operational component610, security control system 600, or an application 679 or the likeaccessing object data file(s) 640). Block 720 provides for verifying anauthorization code associated with the object data file (e.g.,verification module 630 verifying authorization code(s) 620 associatedwith object data file(s) 640).

Disposed within block 720 is optional block 7201, which provides forextracting the authorization code as one or more of a redundancy check,error checking algorithm, checksum code and/or cryptographic hashfunction (e.g., verification module 630 extracting authorization code(s)620 wherein authorization code(s) 620 are checksum codes and/orcryptographic hash functions). Also disposed within block 720 isoptional block 7202, which provides for removing a header from theobject data file, the header including the authorization code (e.g.,verification module 630 removing a header from object data file(s) 640wherein the header includes authorization code(s) 620). Followingoptional block 7202 is optional block 7203 which provides fortransmitting the authorization code to a control system operably coupledto the operational component (e.g., transceiver 670 transmittingauthorization code(s) 620 to or from external control system 675 coupledto operational component 610). Following optional block 7203 is optionalblock 7204 which provides for receiving an enabling signal from thecontrol system to enable reification of the one or more objects (e.g.,external control system 675 or security control system 600 sending anenabling signal or disabling signal to enable or prevent reification ofoutput objects 650).

Also included in block 720 is optional block 7205 which provides forcomparing the authorization code to a stored list of authorization codesaccessible to the an operational component (e.g., comparator 683comparing authorization code(s) 620 to stored list 625 of authorizationcodes accessible to an operational component 610).

Also included in block 720 is optional block 7206 which provides forreceiving an indication from a control system operably coupled to the anoperational component that the authorization code has been verified asvalid (e.g., transceiver 670 receiving an indication from externalcontrol system 675 coupled to an operational component 610 thatauthorization code(s) 620 are verified as valid). Also included in block720 is optional block 7207 which provides for verifying theauthorization code wherein the authorization code is associated withcopyright protection of the object data file, the object data fileincluding one or more reproducible object files to enable the anoperational component to implement a function (e.g., reify) regardingthe one or more objects.

Also included in block 720 is optional block 7208 which provides forverifying the authorization code wherein the authorization code isassociated with a licensing status associated with the one or moreobjects and/or object data file, the licensing status includinglicensing restrictions 672 indicative of one or more of a royaltystatus, an expiration date pertaining to a license, and/or a number ofmanufacturing runs permitted according to the license (e.g.,verification module 630 verifying authorization code(s) 620 associatedwith a licensing status associated with objects 650 and/or object datafile(s) 640, the licensing status indicating a royalty status, anexpiration date for the license and/or a number of manufacturing runsunder the license).

Also disposed in block 720 is optional block 7209 which provides forverifying the authorization code wherein the authorization code enablesa determination of an applicable pre-condition such as payment statusand/or an authorization status under a reification agreement (e.g.,verification module 630 verifying authorization code(s) 620, wherein theauthorization code(s) 620 enables a determination of a payment statusand/or an authorization status under a permission agreement 674 to reifyobjects 650 described by an object data file(s) 640).

The method continues in FIG. 7B illustrating block 730, which providesfor controlling operation of the an operational component to enable orprevent an operational function regarding the one or more objectspursuant to the authorization code in accordance with one or morepredetermined conditions (e.g., verification module 630 interacting withan operational component 610 to enable or prevent an operationalfunction regarding output objects 650 or output data 652 or outputresult 654 in accordance with licensing restrictions 672 and/orpermission agreement 674).

Disposed within block 730 is shown optional block 7300 which providesfor enabling or preventing manufacturing using one or more of a polymer,ABS (Acrylonitrile/butadiene/styrene), ABSi (ABS with high impactstrength), ABS M-30 (Acrylonitrile/butadiene/styrene), PC(Polycarbonate), PC-ISO (Polycarbonate-ISO), PC/ABS (Polycarbonate/ABSBlend), PPSF (Polyphenylsulfone), clear and/or colored resin (e.g.verification module 630 enabling or preventing manufacturing using oneor more of a polymer, ABS (Acrylonitrile/butadiene/styrene), ABSi (ABSwith high impact strength), ABS M-30 (Acrylonitrile/butadiene/styrene),PC (Polycarbonate), PC-ISO (Polycarbonate-ISO), PC/ABS(Polycarbonate/ABS Blend), PPSF (Polyphenylsulfone), clear and/orcolored resin).

Also disposed within block 730 is optional block 7301 which provides forenabling or preventing rapid prototyping, three-dimensional printing,two-dimensional printing, freeform fabrication, solid freeformfabrication, and stereolithography (e.g., verification module 630enabling or preventing rapid prototyping, three-dimensional printing,two-dimensional printing, freeform fabrication, solid freeformfabrication, and stereolithography in production embodiments 684-699).

Also disposed within block 730 is optional block 7302, which providesfor enabling or preventing one or more of stereolithography (SLA),selective laser sintering (SLS), computer numerical control (CNC), andfused deposition modeling (FDM) if the authorization code meets the oneor more predetermined conditions (e.g. verification module 630 enablingor preventing according to authorization code(s) 620 stereolithography(SLA), selective laser sintering (SLS), computer numerical control(CNC), and fused deposition modeling (FDM) in manufacturing productionembodiments 684-699).

Also disposed within block 730 is optional block 7303, which providesfor enabling or preventing three-dimensional manufacturing using one ormore of metal, wood, ice, stone, glass, polymer, composite, laminate,semiconductors, printed circuit boards, integrated circuits, nuclearmaterials, pharmaceuticals, neutraceuticals, edible substances, sand,ceramic materials, aluminum, silicon, carbides, silicon nitrides,silicon carbides, metal/ceramic combinations including aluminum/siliconnitride, aluminum/silicon carbide, aluminum/zirconia andaluminum/aluminum nitride including materials alterable by chemicalprocessing, mixing, combustion, friction, heating and cooling if theauthorization code meets the one or more predetermined conditions (e.g.,verification module 630 enabling or preventing three-dimensionalmanufacturing and the like if authorization code(s) 620 meetpredetermined conditions).

Also disposed within block 730 is optional block 7304, which providesfor enabling or preventing two-dimensional manufacturing using one ormore of skin, textiles, edible substances, paper, silicon printing ifthe authorization code meets the one or more predetermined conditions(e.g., verification module 630 enabling or preventing two-dimensionalmanufacturing and the like according to predetermined conditions met ornot met by authorization code(s) 620).

Also disposed within block 730 is optional block 7305, which providesfor enabling or preventing subtractive manufacturing, including enablingor preventing drilling, milling, grinding, machining, polishing,patterning, etching, turning, laser cutting, waterjet cutting, plasmacutting, wire electrical discharge cutting, cold forging, warm forging,and hot forging metal fabrication, if the authorization code meets theone or more predetermined conditions (e.g., verification module 630enabling or preventing subtractive and/or additive type manufacturing inproduction embodiments 684-699).

Block 730 continues in FIG. 7C illustrating optional block 7306 withinblock 730, which provides for enabling or preventing one or more of thefollowing types of manufacturing in accordance with the authorizationcode: computer numerical controlled fabrication, micro-fabrication,injection molding, additive manufacturing, robotic production,packaging, engraving, casting, plating, coating, glazing, laminating,and bonding (e.g., verification module 630 enabling or preventingmanufacturing production embodiments 684-699 in accordance withauthorization code(2) 620).

Block 730 further includes optional block 7307, which provides forenabling or preventing functioning of a physical aspect of the anoperational component if the authorization code meets the one or morepredetermined conditions (e.g., verification module 630 enabling orpreventing functions of an aspect of an operational component 610 ifauthorization code(s) 620 meet predetermined conditions).

Block 730 further includes optional block 7308, which provides forenabling or preventing a read function if the authorization code isaccepted by a control system operably coupled to the operationalcomponent (e.g., verification module 630 enabling or preventing a readfunction to enable reading object data file(s) 640 if authorizationcode(s) 620 are approved by external control system 675 coupled tooperational component 610).

Block 730 further includes optional block 7309 which provides forenabling or preventing a physical aspect of the operational component tofunction if the authorization code matches a stored list of codesaccessible by a control system operably coupled to the operationalcomponent (e.g., verification module 630 enabling or preventing aphysical aspect of operational component 610 to function ifauthorization code(s) 620 matches a one or more codes in a stored listof codes 625 accessible by external control system 675 or securitycontrol system 600 coupled to operational component 610).

Further disposed within block 730 is optional block 7310 which providesfor enabling or preventing the object data file to become readable bythe operational component if the authorization code passes a comparefunction associated with a machine identifier (e.g., verification module630 enabling or preventing readability of object data file(s) 640 byoperational component 610 if authorization code(s) 620 passes acomparison function via comparator 683 with a machine identifier).

Further disposed within block 730 is optional block 7311, which providesfor enabling or disabling an operational function dependent on one ormore of the following predetermined conditions: benchmark comparison,temporal milestone, time period restriction, production quantitylimitation, production machine qualification, operator qualification,event occurrence, and quality certification (e.g., enabling or disablingproduction embodiments 684-699 in accordance with predeterminedconditions such as licensing restrictions 672 or permission agreement674).

Further disposed within block 730 is optional block 7312, which providesfor enabling or disabling one or more of the following types ofoperational components: chemical process apparatus, product packaging,injection molding unit, subtraction machine, additive manufacture unit,two-dimensional production technique, three-dimensional productiontechnique, stamping machine, extrusion machine, melting machine,die-casting machine, solidifying machine, manufacturing system, rapidprototyping device, and robotic production line (e.g., enabling ordisabling operational components and processes 684-699).

Referring now to FIG. 7D, the method continues with block 740, whichprovides for receiving the object data file at a buffer for theoperational component (e.g., transceiver 670 receiving object datafile(s) 640 at buffer 660 for operational component 610). Block 750provides for sending an acknowledgment that the object data file wasreceived by the operational component to a source of the object datafile (e.g., transceiver 670 sending an acknowledgement that object datafile(s) 640 was received by operational component 610 to a source ofobject data file(s) 640).

Block 760 provides for processing the object data file in the buffer toverify a request to instantiate the object data file (e.g., verificationmodule 630 processing object data file(s) 640 in buffer 660 to verify arequest to instantiate object data file(s) 640).

Block 770 provides for receiving the authorization code at a buffer, thebuffer configured to notify an application if the object data file isloaded in the buffer, the object data file including one or more of aproduction model file and/or a computer-aided design (CAD) solid modelfile and/or a computer-aided manufacturing (CAM) file (e.g., buffer 660receiving authorization code(s) 620, buffer 660 then notifying anapplication 679 that object data file(s) 640 is loaded). Disposed withinblock 770 is optional block 7702, which provides for extracting theauthorization code from the object data file in the buffer, theauthorization code required to enable the operational component toacknowledge the object data file as a valid file (e.g., buffer 660extracting authorization code(s) 620 to enable operational component 610to acknowledge object data file(s) 640 as a valid file).

Referring now to FIG. 8, a flow diagram illustrates a method inaccordance with various embodiments for securely controlling anoperational component (block 810). Another possible feature shown inblock 812 includes obtaining access to an object data file configured tocreate or produce or duplicate or process or test one or more objects(e.g., an operational component 610 accessing an object data file 640).Further method features may include verifying validity of anauthorization code associated with the object data file as shown inblock 814 (e.g., verification module 630 confirming validity ofauthorization code 620 associated with an object data file 640); andresponsive to said verifying validity, controlling the operationalcomponent by enabling or preventing its functional activation based oncompliance with one or more predetermined conditions as shown in block816 (e.g., verification module 630 accessing pre-conditions of licensingrestriction 672 and/or permission agreement 674 before allowingactivation of operational component 610).

A further method feature shown in block 828 may include confirming thevalidity of the authorization code by one or more of a digitalcertificate, private/public key, redundancy check, error checkingalgorithm, checksum code and/or cryptographic hash function (e.g.,verification module 630 obtaining authorization code 620 with associatedsecurity features)

Yet another exemplary feature shown in block 820 may provide controllingthe operational component based on compliance with the predeterminedcondition that includes a licensing status regarding an output involvingthe operational component. Related aspects are shown in optional block822 which provides for determining a licensing status regarding anobject output, and in block 824 which provides for determining alicensing status regarding a data output, and in block 826 whichprovides for determining a licensing status regarding a result output.An additional exemplary feature shown in block 830 provides for enablingor disabling the operational component dependent on one or more of thefollowing predetermined conditions: benchmark comparison, temporalmilestone, time period restriction, output quantity limitation, machinequalification, operator qualification, event occurrence, and qualitycertification. (e.g., verification module 630 confirming applicablepreconditions 672, 674 associated with a machine identifier foroperational component 610).

As disclosed herein, the exemplary system, apparatus and computerprogram product embodiments shown in FIGS. 1-2, 4, and 6 along withother components, devices know-how, skill and techniques that are knownin the art have the capability of implementing and practicing themethods and processes shown in FIGS. 3A-3D, 5A-5C, 7A-7D, and 8.However, it is to be further understood by those skilled in the art thatother systems, apparatus and technology may be used to implement andpractice such methods and processes.

It will also be understood that the various methods and systemsdisclosed herein include exemplary implementations for asecurity-activated operational component. Possible embodiments includebut are not limited to obtaining access to an object data fileconfigured to implement various functional operation regarding one ormore objects; verifying validity of an authorization code associatedwith the object data file; and controlling operation of the operationalcomponent to enable or prevent its activation pursuant to theauthorization code in accordance with one or more predeterminedconditions.

Those with skill in the computing arts will recognize that the disclosedembodiments have relevance to a wide variety of applications andarchitectures in addition to those described above. In addition, thefunctionality of the subject matter of the present application can beimplemented in software, hardware, or a combination of software andhardware. The hardware portion can be implemented using specializedlogic; the software portion can be stored in a memory or recordingmedium and executed by a suitable instruction execution system such as amicroprocessor.

While the subject matter of the application has been shown and describedwith reference to particular embodiments thereof, it will be understoodby those skilled in the art that the foregoing and other changes in formand detail may be made therein without departing from the spirit andscope of the subject matter of the application, including but notlimited to additional, less or modified elements and/or additional, lessor modified blocks performed in the same or a different order.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems. Theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skilled in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.)

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,Specific examples of operably couplable include but are not limited tophysically mateable and/or physically interacting components and/orwirelessly interactable and/or wirelessly interacting components and/orlogically interacting and/or logically interactable components.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems in the fashion(s)set forth herein, and thereafter use engineering and/or businesspractices to integrate such implemented devices and/or processes and/orsystems into more comprehensive devices and/or processes and/or systems.That is, at least a portion of the devices and/or processes and/orsystems described herein can be integrated into comprehensive devicesand/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such comprehensive devices and/or processes and/or systemsmight include, as appropriate to context and application, all or part ofdevices and/or processes and/or systems of (a) an air conveyance (e.g.,an airplane, rocket, hovercraft, helicopter, etc.), (b) a groundconveyance (e.g., a car, truck, locomotive, tank, armored personnelcarrier, etc.), (c) a building (e.g., a home, warehouse, office, etc.),(d) an appliance (e.g., a refrigerator, a washing machine, a dryer,etc.), (e) a communications system (e.g., a networked system, atelephone system, a Voice over IP system, etc.), (f) a business entity(e.g., an Internet Service Provider (ISP) entity such as Comcast Cable,Quest, Southwestern Bell, etc.); or (g) a wired/wireless services entitysuch as Sprint, Cingular, Nextel, etc.), etc.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skilled in theart would understand the convention (e.g., “a system having at least oneof A, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral, such a construction is intended in the sense one having skillsin the art would understand the convention (e.g., “a system having atleast one of A, B, or C” would include but not be limited to systemsthat have A alone, B alone, C alone, A and B together, A and C together,B and C together, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purposes ofillustration and are not intended to be limiting, with the true scopeand spirit being indicated by the following claims.

1. A method for securely controlling an operational component,comprising: obtaining access to an object data file configured to createor produce or duplicate or process or test one or more objects;verifying validity of an authorization code associated with the objectdata file; and responsive to said verifying validity, controlling theoperational component by enabling or preventing its functionalactivation based on compliance with one or more predeterminedconditions.
 2. The method of claim 1 further comprising: receiving theobject data file at a buffer for the operation component; sending to asource of the object data file an acknowledgment that the object datafile was received by the operational component.
 3. The method of claim 1wherein the obtaining access includes: obtaining access to the objectdata file that includes one or more of operational instructions and/or aproduction model file and/or a computer-aided design (CAD) solid modelfile and/or a computer-aided manufacturing (CAM) file.
 4. The method ofclaim 1 wherein the verifying validity of the authorization codeassociated with the object data file includes: confirming the validityof the authorization code by one or more of a digital certificate,private/public key, redundancy check, error checking algorithm, checksumcode and/or cryptographic hash function.
 5. The method of claim 1wherein the verifying validity of the authorization code associated withthe object data file includes: removing a header from the object datafile, the header including the authorization code; and transmitting theauthorization code to a security control system operably coupled to theoperational component.
 6. The method of claim 5 further comprising:enabling activation of the operational component upon receipt of anauthorization status signal from the control system.
 7. The method ofclaim 5 further comprising: preventing activation of the operationalcomponent upon receipt of an authorization status signal from thecontrol system.
 8. The method of claim 1 wherein the verifying validityof the authorization code associated with the object data file includes:comparing the authorization code to a stored list of authorization codesaccessible to the operational component.
 9. The method of claim 1wherein the verifying validity of the authorization code associated withthe object data file includes: verifying the authorization codeassociated with copyright protection of the object data file, the objectdata file
 10. The method of claim 1 wherein the controlling theoperational component includes: controlling the operational componentbased on compliance with the predetermined condition that includes alicensing status regarding an object output involving the operationalcomponent.
 11. The method of claim 1 wherein the controlling theoperational component includes: controlling the operational componentbased on compliance with the predetermined condition that includes alicensing status regarding a data output involving the operationalcomponent.
 12. The method of claim 1 wherein the controlling theoperational component includes: controlling the operational componentbased on compliance with the predetermined condition that includes alicensing status regarding a result output involving the operationalcomponent.
 13. The method of claim 1 wherein the controlling theoperational component includes: enabling or preventing a manufacturingoperation using one or more polymer materials.
 14. The method of claim 1wherein the controlling the operational component includes: enabling orpreventing a production operation involving one or more of thefollowing: rapid prototyping, additive manufacturing, subtractivemanufacturing, three-dimensional manufacturing or printing,two-dimensional manufacturing or printing, freeform fabrication, andstereolithography.
 15. The method of claim 1 wherein the controlling theoperational component includes: enabling or preventing functioning of aphysical aspect of the operational component based on compliance withthe one or more predetermined conditions.
 16. The method of claim 1wherein the controlling the operational component includes: enabling orpreventing a read function of the object data file based on compliancewith the one or more predetermined conditions.
 17. The method of claim 1wherein the controlling the operational component includes: enabling ordisabling one or more of the following types of operational components:production device, testing device, creative tool, duplication unit,packaging assembly, chemical process apparatus, injection molding unit,subtraction machine, stamping machine, extrusion machine, meltingmachine, die-casting machine, solidifying machine, custom manufacturing,rapid prototyping device, and robotic manufacturing line.
 18. A computerprogram product comprising a computer readable medium configured toperform one or more acts for securely controlling an operationalcomponent, the one or more acts comprising: one or more instructions forobtaining access to an object data file configured to create or produceor duplicate or process or test one or more objects;; one or moreinstructions for verifying validity of an authorization code associatedwith the object data file; and one or more instructions responsive tosaid verifying validity to control the operational component by enablingor preventing its functional activation based on compliance with one ormore predetermined conditions.
 19. The computer program product of claim18 wherein the one or more instructions for verifying validity of theauthorization code includes: one or more instructions for confirmingvalidity of the authorization code by one or more of a digitalcertificate, private/public key, redundancy check, error checkingalgorithm, checksum code and/or cryptographic hash function.
 20. Thecomputer program product of claim 18 wherein the one or moreinstructions for the verifying validity of the authorization codeincludes: one or more instructions for comparing the authorization codeto a stored list of authorization codes accessible to the operationalcomponent.
 21. The computer program product of claim 18 wherein the oneor more instructions for controlling the operational component includes:one or more instructions for controlling the operational component basedon compliance with the predetermined condition that includes a licensingstatus indicative of one or more of a royalty status, an expiration datepertaining to a license, and/or a number of manufacturing runs permittedaccording to the license.
 22. The computer program product of claim 18wherein the one or more instructions for controlling the operationalcomponent includes: one or more instructions for enabling or preventinga physical aspect of the operational component to function if theauthorization code matches a stored list of codes accessible by acontrol system operably coupled to the operational component.
 23. Thecomputer program product of claim 18 wherein the one or moreinstructions for controlling the operational component includes: one ormore instructions for enabling or preventing the object data file tobecome readable by the operational component if the authorization codepasses a compare function associated with a machine identifier.
 24. Thecomputer program product of claim 18 wherein the one or moreinstructions for the controlling the operational component includes: oneor more instructions for enabling or disabling the operational componentdependent on one or more of the following predetermined conditions:benchmark comparison, temporal milestone, time period restriction,output quantity limitation, machine qualification, operatorqualification, event occurrence, and quality certification.
 25. Thecomputer program product of claim 18 wherein the one or moreinstructions for controlling the operational component includes: one ormore instructions for enabling or disabling one or more of the followingtypes of operational components: production device, testing device,creative tool, duplication unit, packaging assembly, chemical processapparatus, injection molding unit, subtraction machine, stampingmachine, extrusion machine, melting machine, die-casting machine,solidifying machine, custom manufacturing, rapid prototyping device, androbotic manufacturing line.
 26. A security system for one or moreoperational components comprising: an authorization code that requiresone or more pre-conditions to control an operational component that isconfigured to create or produce or duplicate or process or test anobject; a verification module capable of enabling or disabling theoperational component, the verification module operably coupled to theauthorization code and operably coupled to the operational component;and an object data file associated with the authorization code, whereinthe object data file is configured to activate the operational componentbased on confirmation from the verification module.
 27. The securitysystem of claim 26 wherein the verification module is configured forcontrolling operation of the production device based on compliance withthe one or more pre-conditions.
 28. The security system of claim 26further comprising: a buffer coupled to the verification module, thebuffer configured to send an acknowledgement that the object data filewas received by the operational component.
 29. The security system ofclaim 26 wherein the buffer is adapted for processing the object datafile in the buffer to verify a request to implement the object datafile.
 30. The security system of claim 26 wherein the buffer is adaptedto receive the authorization code and notify the verification modulethat an object data file is loaded in the buffer.
 31. The securitysystem of claim 26 wherein the object data file is one or more ofoperational instructions, and/or a production model file and/or acomputer-aided design (CAD) solid model file and/or a computer-aidedmanufacturing (CAM) file.
 32. The security system of claim 26 whereinthe verification module is configured to extract the authorization codefrom the object data file, the authorization code configured to enablethe operational component to acknowledge the object data file as a validfile.
 33. The security system of claim 26 wherein the verificationmodule is configured for validating the authorization code based on oneor more of a digital certificate, private/public key, redundancy check,error checking algorithm, checksum code and/or cryptographic hashfunction.
 34. The security system of claim 26 wherein the verificationmodule includes: a parser configured for removing a header from theobject data file, the header including the authorization code; and atransceiver configured for transmitting the authorization code to acontrol system operably coupled to the operational component and/orconfigured for receiving an enabling signal from the control system toactivate the operational component.
 35. The security system of claim 26wherein the verification module includes a comparator, the comparatorconfigured for comparing the authorization code to a stored list ofauthorization codes accessible to the operational component.
 36. Thesecurity system of claim 26 wherein the verification module isconfigured for receiving an indication from a control system operablycoupled to the operational component that the authorization code hasbeen verified as valid.
 37. The security system of claim 26 wherein theverification module is configured for verifying the authorization codewherein the authorization code is associated with copyright protectionof the object data file, the object data file including one or morereproducible object files to activate the operational component.
 38. Thesecurity system of claim 26 wherein the verification module isconfigured for verifying the authorization code associated with alicensing status regarding the object and/or regarding the object datafile, the licensing status indicative of one or more of a royalty, anexpiration date, an operational restriction, and/or a permitted numberof manufacturing runs.
 39. The security system of claim 26 wherein theverification module is configured for verifying the authorization codewherein the authorization code enables a determination of a paymentstatus and/or an authorization status under an operational permissionagreement.
 40. The security system of claim 26 wherein the verificationmodule is configured for enabling or preventing manufacturing that usesone or more of a polymer, ABS (Acrylonitrile/butadiene/styrene), ABSi(ABS with high impact strength), ABS M-30(Acrylonitrile/butadiene/styrene), PC (Polycarbonate), PC-ISO(Polycarbonate-ISO), PC/ABS (Polycarbonate/ABS Blend), PPSF(Polyphenylsulfone), clear and/or colored resin.
 41. The security systemof claim 26 wherein the verification module is configured for enablingor preventing one or more of stereolithography (SLA), selective lasersintering (SLS), computer numerical control (CNC), and fused depositionmodeling (FDM) if the authorization code meets the one or morepre-conditions.
 42. The security system of claim 26 wherein verificationmodule is configured for enabling or preventing three-dimensionalmanufacturing that uses one or more of metal, wood, ice, stone, glass,polymer, composite, laminate, semiconductors, printed circuit boards,integrated circuits, nuclear materials, pharmaceuticals,neutraceuticals, edible substances, sand, ceramic materials, aluminum,silicon, carbides, silicon nitrides, silicon carbides, metal/ceramiccombinations including aluminum/silicon nitride, aluminum/siliconcarbide, aluminum/zirconia and aluminum/aluminum nitride includingmaterials alterable by chemical processing, mixing, combustion,friction, heating and cooling if the authorization code meets the one ormore pre-conditions.
 43. The security system of claim 26 whereinverification module is configured for enabling or preventingtwo-dimensional manufacturing that uses one or more of skin, textiles,edible substances, paper, silicon printing if the authorization codemeets the one or more pre-conditions.
 44. The security system of claim26 wherein verification module is configured for enabling or preventingsubtractive manufacturing, including enabling or preventing drilling,milling, grinding, machining, polishing, patterning, etching, turning,laser cutting, waterjet cutting, plasma cutting, wire electricaldischarge cutting, cold forging, warm forging, and hot forging metalfabrication, if the authorization code meets the one or morepre-conditions.
 45. The security system of claim 26 wherein theverification module is configured for enabling or preventing one or moreof the following types of manufacturing in accordance with theauthorization code: computer numerical controlled fabrication,micro-fabrication, injection molding, additive manufacturing, roboticproduction, packaging, engraving, casting, plating, coating, glazing,laminating, and bonding.
 46. The security system of claim 26 whereinverification module is configured for enabling or preventing functioningof a physical aspect of the operational component if the authorizationcode meets the one or more predetermined conditions.
 47. The securitysystem of claim 26 wherein the verification module is configured forenabling or preventing a read function if the authorization code isaccepted by a control system operably coupled to the operationalcomponent.
 48. The security system of claim 26 wherein verificationmodule is configured for enabling or preventing a physical aspect of theoperational component to function dependent on a matching comparison ofthe authorization code with a stored list of codes accessible by acontrol system operably coupled to the operational device.
 49. Thesecurity system of claim 26 wherein verification module is configuredfor enabling or preventing the object data file to become readable bythe operational component if the authorization code passes a comparefunction associated with a machine identifier.
 50. The security systemof claim 26 wherein the verification module is configured for enablingor disabling the operational component dependent on one or more of thefollowing predetermined conditions: benchmark comparison, temporalmilestone, time period restriction, output quantity limitation, machinequalification, operator qualification, event occurrence, and qualitycertification.
 51. The security system of claim 26 wherein theverification module is configured for enabling or disabling one or moreof the following types of production devices: chemical processapparatus, product packaging, injection molding unit, subtractionmachine, additive manufacture unit, two-dimensional productiontechnique, three-dimensional production technique, stamping machine,extrusion machine, melting machine, die-casting machine, solidifyingmachine, manufacturing system, rapid prototyping device, and roboticproduction line.